Welcome to Gary Gulane's WebPage

Common Troubleshooting Techniques & Strategies

Here are five common-sense techniques and strategies to solve common computer hardware problems.

1) Trial-and-error

Personal computers are highly modular by design. The most powerful trouble-shooting technique is to isolate the problem to a specific component by trial-and-error. Swap compatible components and see if the system still works. Try different peripherals on different machines and see if the same problem occurs. Make one change at a time.

(2) "It's the cable, s-----."

More than 70% of all computer problems are related to cabling and connections. Ensure all cables are connected firmly. IDE and floppy ribbon cables and power cables can often go loose. Ensure microprocessor, memory modules, and adapters such as video card and sound card are inserted correctly and didn't "pop-up" during transportation.

(3) Don't be frustrated!

Don't be afraid of computer problems. It is often the best opportunity to learn. Trouble-shooting is part of the fun of owning a computer. Imagine the satisfaction you could get by solving a problem yourself.

Of course the fun could ran out quickly once you are frustrated and have spent too much time on the same problem. If you feel frustrated, it's time to leave it for a while and go back with some new ideas or call someone who can help. Rule of thumb: You shouldn't spend more than three hours on the same problem at one time.

(4) Take notes!

Take notes of what you have done and all the error messages. You may need to use them later. For instance, when you see an unusual blue screen with an error message, copy the entire message onto a piece of paper. In many situations, that message may point to the right direction in getting the problem solved quickly.

(5) Take a look?

It's OK to open a computer case and take a look inside. There is only 5V and 12V DC voltage supplied to the components outside the power supply. Those who have never seen the inside of a computer are often amazed by how simple it looks. Of course, still always power down and unplug the power cord first.

Trouble Shooting Tips after Installing a New Hard

Drive

1. Basic Troubleshooting Tips after Installing a New Hard Drive
   Based on Seagate IDE hard drives.
   
   If you have installed your drive and it does not function properly, perform the following basic checks:
   
   Warning: Always turn off the computer before changing jumpers or unplugging cables and cards. Wear a ground strap or use other antistatic precautions while working on your computer or handling your drive.
   • Verify compatibility. Verify that the host adapter and drive are appropriately matched to each other and to your computer. Refer to the relevant documentation for details.
   • Check all cards. Verify that all cards are seated in their slots on the motherboard and secured with mounting screws.
   • Check all connectors and cables. Make sure all ribbon and power cables are securely connected. Ribbon cables are easily damaged, especially at the connector. Try a new cable that you know is good. Make sure no connector pins are bent. Verify that pin 1 on the interface cable is aligned with pin 1 on the drive and host adapter (see Figure 2 on page 6).
   • Verify jumper settings. Review the instructions in this guide and in your host adapter installation guide. Make sure all appropriate jumpers are installed or removed as necessary.
   • Check your power-supply specifications. Each time you add a new device to your computer, make sure your cornputer's internal power supply can support the total power demand. If necessary, consult your dealer for a new power supply.
   • Verify the drive-type settings in the system setup program. The drive-type settings in the system BIOS must not exceed the physical specifications of your drive. Also, the settings must not exceed the limitations set by the operating system and BIOS.
   • Check for viruses. Before you use someone else's diskette in your system for the first time, scan the diskette for viruses.

2. After you install your new drive, your computer will not boot, and no error message appears on the screen.
   
   Check your computer manual or BIOS manufacturer to determine whether your BIOS supports drives that have more than 4,092 cylinders. If your system has this limitation, use the following procedure to configure your computer:
   • Turn off your computer, open the case, and remove your new drive.
     
     CAUTION: To avoid electrostatic discharge damage to your computer or hard drive, make sure you are well grounded before touching the drive, cable, connector or jumpers.
   • Move the jumper on the alternate-capacity jumper, as shown in Figure 6. This causes the drive to appear to your BIOS as having a 2.1-Gbyte capacity (4,092 cylinders, 16 heads, 63 sectors per track). You may need third-party partitioning software, such as Disk Manager, to achieve full capacity of the drive.
   • Remount your drive in the computer and replace the computer cover.
   • Insert a bootable system diskette into drive A and turn on the computer. It should boot from drive A and automatically detect the new drive as a 2.1 -Gbyte drive.
   • Insert your Disc Wizard diskette into drive A and type A:XDM. Then press ENTER. This runs the Disk Manager program.
   • Follow the Disk Manager instructions to install the dynamic drive overlay and to partition and format your new drive to its full capacity.
   • After Disk Manager is done, reboot your system. You should see the Disk Manager banner and be able to access the full capacity of your new drive.

3. The screen remains blank when you power up the system.
   If the steps listed above do not remedy this problem, try the following:

1.  
   • Make sure the monitor is plugged in and turned on.
   • Check all cards.
   • Make sure the video card is seated in its slot and secured with mounting screws.
   • Turn off the computer and remove the drive host adapter. If the screen turns on after you reboot, the host adapter may be incompatible or defective. If so, see your dealer.

4. The system does not recognize the drive.
   • Check all cables.
   • Make sure the power supply is adequate for system needs.
   • Reboot the computer and listen to make sure the drive motor starts up. If the drive is very quiet, it may be difficult to hear its discs reach operating speed. If the drive motor does not start up, recheck all drive cables.
   • Verify that for each drive, a drive-type is listed in the system setup program.
   • Try rebooting your computer by pressing the CTRL, ALT and DELETE keys simultaneously. If the drive is recognized after you reboot the system, the computer BIOS test may be completing before the drive is ready.
     One solution is to slow the processor speed during startup. If your computer has a turbo switch, set it to slow speed before turning the computer on. If there is no turbo switch, you may be able to use keyboard commands; see your computer manual for details. After the computer is up and running, return the processor to the fast speed.
     Another solution is to warm-boot your computer after every power-on.
   • Check for I/O address conflicts. To isolate the conflict, verify that the drive and host adapter are compatible with your computer. Turn off the computer and remove all the peripheral adapter cards except for the video card and host adapter. If the computer recognizes the drive when you reboot the computer, turn off the computer. Reinstall the other peripheral cards, one at a time, until the conflict reoccurs. After you have isolated the source of the address conflict, you can resolve the conflict by changing the 1/0 address of the peripheral that appears to cause the conflict.
   • If Disk Manager has installed the DDO on your hard drive and you have booted directly from a diskette, the information in the boot record for the drive may not have been loaded. Make sure there is no diskette in drive A and reboot. If you want to boot from the diskette, follow the "Booting with a Diskette" instructions under "Advanced Disk Manager Options" on page 20.

5. The dealer partitioned and formatted the drive for you in the store, but the drive does not respond when you install it.
   • Reboot the computer and make sure the drive spins up.
   • Check all cables.
   • Make sure the power supply is adequate for system needs.
   • Make sure the DOS or Windows version the dealer used to partition and format the drive is the same version you have installed in your computer. If it isn't, see your dealer.
   • Verify the drive-type values in the system setup program. You must install the drive using the same drive-type values your dealer used to partition the drive.
   • Check for 1/0 address conflicts between peripheral cards.
   • Check for viruses.

6. The system hangs in FDISK or fails to create or save the partition record.
   • Check all cables.
   • Your setup system diskette may be corrupted. Try using a backup diskette.
   • Make the partitions smaller.
   • Change the interrupt jumper setting on the host adapter.
   • Some BIOS have a Track 0 protection feature that protects Track 0 from viruses. This may cause FDISK to hang the system. You must disable this feature in the system setup program before you can use FDISK. See your computer reference guide for assistance. Be sure to re-enable this important feature when FDISK is done.

7. The system error message, "Drive not Ready," appears.
   • Check all cable connections. Make sure pin 1 of the drive is connected to pin 1 of the hard-disc controller or host adapter.
   • Make sure the power supply is adequate for system needs.
   • Reboot the computer and make sure the drive spins up.

8. The FDISK error message, "No Fixed Disk Present," appears.
   • Make sure the power supply is adequate for system needs.
   • Verify the drive-type values in the system setup program.
   • Check for 1/0 address conflicts.

9. The drive does not format to full capacity.
   • Verify the drive-type values in the system setup program. One of the following problems may have occurred:
   • The values may be set with an incorrect translation characteristic.
   • You may have entered a parameter value that exceeds the physical capacity of the drive.
   • You entered a translation characteristic that does not take full advantage of the drive's capacity.
   • The drive's physical specifications exceed the translation limits imposed by the BIOS.
     
     CAUTION: If you change the drive-type values in the system setup program, you must partition and format the drive again. This erases data on the drive.
   • If you have partitioned the drive into individual logical drives, you may need to make the partitions smaller to access the full drive capacity.
   • If your computer supports LBA mode, you may need to enable LBA mode in the system setup program to access the full capacity of the drive. Refer to your computer's reference guide to find out how to enable LBA.
   • Your computer may not support drives that have more than 4,092 cylinders. Follow the instructions on page 25 for After you install your new drive, your computer will not boot, and no error message appears on the screen.

10. The DOS message "Disk Boot Failure," "Non-System Disk" or "No ROM Basic - SYSTEM HALTED" appears.
    • Reinstall the DOS system files using the DOS SYS utility.
    • Check all cables.
    • Use FDISK to verify that the primary partition is active.
    • Check for viruses.

11. The system error message, "HDD controller failure" appears.
    • Confirm the jumper settings on the drive.
    • Verify the drive-type settings in the system setup program.

Troubleshooting Tips for a  Motherboard

More than 70% of all computer problems are related to cabling and connections. Ensure all cables are connected and connected firmly. IDE and floppy ribbon cables and power cables can often go loose. Ensure microprocessor, memory modules, and adapters such as video card are inserted correctly and didn't "pop-up" due to vibration.

System has no power at all. Power light does not illuminate, fan inside the power supply does not turn on, and indicator light on keyboard does not turn on.

System inoperative. Keyboard lights are on, power indicator lights are lit, and hard drive is spinning.

System does not boot from hard disk drive, can be booted from floppy disk drive.

System only boots from Floppy Disk. Hard Disk can be read and applications can be used, but booting from Hard Disk is impossible.

Error message reading "SECTOR NOT FOUND" or other error messages indication certain data is not allowed to be retrieved.

Disk formatted on IBM PS/2 will not operate with this system.

After install an expansion card (network card, tape drive card, etc.) the system no longer works properly.

Screen message says "Invalid Configuration" or "CMOS Failure."

Screen is blank.

System does not boot from hard disk drive, can be booted from floppy disk drive.

Problem

Screen goes blank periodically.

Keyboard failure.

No color on screen.

Floppy drive lights stays on.

Error reading drive A:

C: drive failure.

Cannot boot system after installing second hard drive.

Missing operating system on hard drive.

Certain keys do not function.

Keyboard is locked, no keys function.

Troubleshooting Tips for a New Network Card

1. If you can't connect to a server or if Windows reports an error after you double-click Network Neighborhood, try the following first:
   • Make sure you're using the drivers that are on the drivers disk that ships with the network interface card (NIC).
   • Make sure the driver is loaded and the protocols are bound. Check the Device Properties list for trouble indicators (an "X" or "!" symbol).
   • Test the NIC adapter with the diagnostic utilities that often came with the driver installation.
   • Check with your LAN administrator - you may need to install additional networking software.
2. If the problem persists, follow these guidelines:
   • Make sure the cable is installed properly. The network cable must be securely attached at both RJ45 connections (adapter and hub). The maximum allowable distance from adapter to hub is 100 meters. If the cable is attached and the distance is within acceptable limits but the problem persists, try a different cable. If you're directly connecting two computers without a hub or switch, use a crossover cable.
   • Try another network cable.
   • Check the LED Lights on the NIC. Before the LEDs can be used for troubleshooting, the network interface card (NIC) must be connected to the network and the network driver must be installed. Most NICs come with LEDs near the connection. The meaning of the LED signals may be different from one manufacturer to the other. Here is a common LED description for 3COM 10/100BT dual speed NIC. Please consult your NIC manual for any difference.

3. The computer hangs when the drivers are loaded.
   • Change the PCI BIOS interrupt settings. See your NIC and system manuals for more details.
   • If you are using EMM386, it must be version 4.49 or newer.
4. Diagnostics pass, but the connection fails or errors occur.
   • At 100BT, use Category 5 wiring and make sure that the network cable is securely attached.
   • At 100BT, connect to a 100BT hub/switch (not 100Base-T4).
   • For NetWare, make sure you specify the correct frame type in your NET.CFG file.
   • Make sure the duplex mode setting on the adapter matches the setting on the switch.
5. The LNK LED doesn't light.
   • Make sure you've loaded the network drivers.
   • Check all connections at the adapter and the hub/switch.
   • Try another port on the hub/switch.
   • Make sure the duplex mode setting on the adapter matches the setting on the hub/switch.
   • Make sure you have the correct type of cable between the adapter and the hub. 100Base-TX requires two pairs. Some hubs require a crossover cable while others require a straight-through cable.
6. The ACT LED doesn't light.
   • Make sure you've loaded the correct network drivers.
   • The network may be idle. Try accessing a server.
   • The adapter isn't transmitting or receiving data. Try another adapter.
   • Make sure you're using two-pair cable for TX wiring.
7. The adapter stopped working without apparent cause.
   • Run the diagnostics program that came with the NIC.
   • Try reseating the NIC in its slot, or try a different slot if necessary.
   • The network driver files may be corrupt or missing. Remove the drivers and then reinstall them.
8. The Wake on LAN (WOL) feature is not working.
   • Make sure the WOL cable is attached and that power is being applied to the computer.
   • Check the BIOS for its WOL setting. Some computers may need to be configured for WOL.
   • Make sure the network cable is fully attached to the adapter.
9. Crossover cable troubleshooting tips. When you work with network cabling, concentrators (hubs or switch), and NICs from different venders, it is possible to connect everything and still have no communication between file servers and workstations.
   When there are several unknown variables, it is difficult to determine which component is broken. Use these tips to isolate the problem.
   • Determine whether your equipment complies with the 10Base-T or 100Base-TX standard. This is particularly important for hubs and switches.
   • Connect a straight-through cable from the PC to the hub. The hub performs an internal crossover so that the signal can go from TD+ to RD+ and TD- to RD- (see How to Make Network Cables). When you look at an RJ-45 connector from the front, pin 1 is identified on the left-hand side when the metal contacts are facing up.
   • Make sure that the TD+ and TD- wires are twisted together , and that the RD+ and RD- wires are twisted together. Using wires from opposing pairs can cause signals to be lost. For a 100Base-TX cable, pins #1 and #2 , and #3 and #6 must be on the same twisted strand.
10. When there is doubt whether a hub is performing correctly, or if the impedance settings are in question, a crossover cable can help you isolate the failing component:
    • Connect a file server and a client PC back to back with a crossover cable to verify that the NIC and network operating system are properly configured.
    • To make a crossover cable, simple connect TD+ to RD+ and TD- to RD-. The cable performs the crossover that is usually performed by the hub. Make sure that two twisted-pair wires are used. If the file server and client PC function together as a small network, then either the existing cabling or the hub is the problem.
    • If there is a proper crossover, the appropriate LED comes on. If there is a straight-through connection, the LED does not light. A blinking LED indicates that there is a polarity mismatch (that is, TD+ to RD- instead of TD+ to RD+).

Troubleshooting Tips for Cases and Power Supplies

·  The most important part of a computer case is its power supply. Unfortunately, it's also the part that has most of the problems for a case. There are two situations when a new power supply may appear dead on arrival (DOA) when they are actually working as described below:

·  Most cases and power supplies these days are made and tested in China and other Asian countries where 220V electricity is used. Desktop computer power supplies do not switch the power voltage automatically. (Most notebook computers do!) If the factory forgets to turn the manual switch back to 110V for the North American market after testing, the power supply would appear DEAD if you use on a 110V-outlet. Therefore, always check the voltage setting on the back of a new power supply FIRST if it appears dead.

·  Do not expect an ATX power supply to work by simply plugging the power and turning on the switch. ATX power supplies are soft-switched on and off by the motherboard and BIOS. Therefore, you must plug it to a working motherboard with a working microprocessor, memory and video card to work. If your computer does not turn on after you turn on the power switch, it may not necessarily mean a dead power supply. The problem might be with the motherboard, microprocessor, memory or video card instead. You must examine all these components to isolate the problem.

·  The most effective technique to tell if a power supply is causing any problem is to use a different one to see if it solves the problem. If everything works with a different power supply, then the new power supply is most likely the troublemaker. Alternatively, you can plug the new power supply to an existing, working computer to see if it works there.

·  Computer cases are highly modular. If your computer case is still under warranty, you don't have to send the entire case back if only one part of it is defective. For instance, send only the power supply back for exchange if only power supply is dead. The same is true for the face panel and cover. This would save you quite a bit of shipping and sometimes downtime.

·  More than 70% of all computer problems are related to cabling and connections. Ensure that you all the power plugs are connected firmly, including power connections to your motherboard and all the drives.

·  Make sure the cooling fan inside the power supply is working all the time. Reach out to feel the fan behind your case often. Clean the fan if necessary. If your case feels warmer than room temperature, check the power supply fan first. Most power supply fans are difficult to replace. You are better off to replace the entire power supply since the new one comes with a brand-new warranty.

·  Before ATX form factor became popular, the compatibility between a power supply and a specific motherboard could be problematic. However, this problem nowadays does not happen very often any more.

·  The rest of a case is mostly mechanical. You should be able to find a way to get around most of the problems if you are mechanically inclined.

Fax/Modem Troubleshooting Tips

My modem is a 56K, but I can connect to the Internet only at slower speed.
The current copper wired telephone lines are limited only to about 53K. If you are connected only to 33.6 or 28.8K, check the following first:

• Is your modem compatible with the modem used at your ISP?
• Is your modem set up to run at full speed?
• What's the maximum speed your ISP allows?
• How far away are you from your ISP?
• Some modems need special initiation strings to get full speed.
• Some conditions are out of your control, such as weather and conditions of the telephone lines in your community.
• Problems may occur when you are dialing through a phone system such as one in a hotel.

Modem answers incoming calls and then returns to the on-hook condition, disconnecting the caller:
This occurs most often when connecting to a UNIX system. In most case, the host does not prefer to see any result or command echo codes. If this is the case, the codes can be disabled by adding E0 Q1 to the modem configuration string.

The modem dials and appears to complete the connection, but the communications software does not enter the correct mode. (The screen remains blank)
This is normally caused by an I/O address or IRQ conflict. Verify that the COM port is not in use by any other serial device and if necessary use another COM port or I/O address setting. Refer to your computer manual on how to determine what serial ports are installed.

The modem dials and appears to complete the connection, but the communications software does not enter the correct mode. (The screen remains blank)

• There may be an I/O conflict (see the solution for the previous problem).
• The Result Codes may have been disabled by the software configuration set up. Check if Q1 is in the configuration or initialization string. If so, change it to Q0.
• Your software may require numeric result codes rather than verbal result codes. Use either V0 for numeric result codes or V1 for verbal result codes in your initiazation or configuration string.
• Some software require full extended result codes (i.e., CONNECT 33600 instead of CONNECT). This can be controlled by the Xn command. X0 sends a summarized code (CONNECT) and X4 sends a full extended code (CONNECT 33600)

The modem does not auto answer
The auto answer mode is determined by the S0 register. If S0 has been set to 0, the modem will not answer. Assign another value to S0 by entering the following command: S0=n, where n = the number of rings to occur before the call is answered (ATS0=2, the modem answers after two rings)

The modem always answers the phone.
Set the S0 register to 0. ATS0=0.

The communications software displays, "No Dial tone."
Make sure that your phone cable is working properly and that it is firmly seated to the phone socket at your phone jack and in the real panel of the modem.

A high pitched squeal is emitted from the external speakers
This phenomenon is "feedback" and occurs when the microphone is pointed at the external speaker or is close enough to pick up the speaker output. This may be remedied by using a unidirectional microphone, making sure that it is pointed away and as far from the speaker as functionally possible. Another option is to use a headset with an attached microphone.

Trouble Shooting Tips after Installing a New Video

Card

The following troubleshooting tips may help if you experience problems.

• Check that the card is seated properly in its expansion slot. Some AGP cards have design flaws and are "well-known" to "pop out" during transportation. For PCI cards, if the problem still exists, try a difference PCI expansion slot.
• Ensure the display cable is securely fastened to the card's display connector.
• Make sure that the display and computer are plugged in and receiving power.
• If necessary, disable any built-in graphics capabilities on your motherboard. For more information, see your computer's manual.
• Make sure you selected the appropriate display device and graphics card when you installed your enhanced driver.
• If you have problems during start-up, start your computer in Safe Mode. In Windows 98, press the F8 key when "Starting Windows 98" appears; or, in Windows 98, press and hold the CTRL key until the Windows 98 Startup Menu appears on the screen. Then select the number for Safe Mode, and press Enter.

Troubleshooting Tips for a Monitors

Here are some basic trouble shooting tips for a monitors:

1. The picture does not appear
   • Check to make sure the signal cable is firmly connected in the socket.
   • Check to see if the computer system's power is ON.
   • Check that the Brightness Control is at the appropriate position, not at the minimum.
2. The Screen is not synchronized
   • Check to make sure the signal cable is firmly connected in the socket.
   • Check that the output level matches the input level of your computer.
   • Make sure the signal timing of the computer system is within the specification of the monitor.
3. The position of the screen is not in the center
   • Adjust the H-Size, H-Phase or V-Size, V-Center controls.
   • Check if the signal timing of the computer system is within the specification of the monitor.
4. The screen is too bright or too dark
   • Check if the Brightness or contrast control is at the appropriate position, not at the maximum or minimum.
   • Check if the specified voltage is applied
   • Check if the signal timing of the computer system is within the specification of the monitor.
   • Especially, check the horizontal frequency.
5. The screen is shaking
   • Move all objects that emit a magnetic field, such as a motor or transformer, away from the monitor.
   • Check if the specified voltage is applied.
   • Check if the signal timing of the computer system is within the specification of the monitor.

Troubleshooting Tips for a New Sound Card

Here are some tips in troubleshooting sound card

No sound is heard from audio (music) CDs
Various conditions may cause this problem. To troubleshoot, check the following:

• Microsoft Volume Control or your mixer program mute options and volume sliders.
• Connect headphones to the stereo phone jack on your CD-ROM drive’s front panel; adjust the volume control settings on the drive. If there is sound from your headphones, check the CD audio cable connection from the CD-ROM drive to the audio card.
• Ensure the speakers are properly connected to the audio card’s output connector.

Joystick port is not working
To troubleshoot, check the following:

• The audio card joystick port conflicts with another joystick port in the system. Disable the audio card joystick port, and use the system’s joystick port.
• The joystick drivers, MSJSTICK.DRV and VJOYD.VXD, may not be installed. Uninstall the joystick, then reinstall to load the drivers. The drivers should come with the driver CD or floppy diskette with your sound card.

Computer hangs or restarts during installation
A hardware conflict may cause the computer to hang or restart during the installation procedure. Check the following to resolve the conflict:

• A hardware conflict with another device in your system.
• Previously installed sound card hardware or software needs to be removed.
• The audio card is not seated in the slot properly.
• PCI bus mastering devices may be interfering with the operation of the audio card. Temporarily remove non-essential PCI bus mastering devices.

Resolving hardware conflicts
Hardware conflicts occur when two or more devices contend for the same resources. Conflicts between your audio card and another device may occur regarding the I/O address, IRQ line, or DMA channel:

1. Right-click the My Computer icon on your desktop, and select Properties. The System Properties dialog appears.
2. Click the Device Manager tab. In the Device Manager, a plus sign(+) represents an expandable list of items. A minus sign (-) represents an expanded list. A circled exclamation mark denotes a conflict.
3. Double-click Sound, video, game controllers. A list of multimedia devices appears.
4. Select your audio card.
5. Choose the Properties button.
6. Click the Resources tab.
7. Uncheck the Use automatic settings option.
8. Change "Settings based on:" if alternate settings are available.
9. Determine the conflict by reviewing the "Conflicting device list".
10. Select the conflicting item in the "Resource Settings" list.
11. Click the Change Settings button.
12. Use the mouse to select a new setting.
13. Select OK to close each of the properties windows, and restart your computer.

Audio card is not automatically detected
To manually configure your audio card for Windows 95/98:

1. Click "Start" on the taskbar, and select Settings from the Start menu.
2. Select Control Panel. The Control Panel group appears.
3. Double-click the Add New Hardware icon. The Add New Hardware Wizard dialog appears.
4. Select Next to continue.
5. Choose Yes to have Windows search for new hardware, then select Next
6. Select Next to continue.
7. Select Finish, and follow the prompts to complete the new hardware installation.

CD does not automatically run when you insert it in the drive
To enable the "Audio insert notification" feature:

1. Right-click the My Computer icon on your desktop, and select Properties. The System Properties dialog appears.
2. Click the Device Manager tab. A list of devices appears.
3. Double-click CD-ROM, and select your CD-ROM drive.
4. Choose the Properties button. The CD-ROM drive properties dialog appears.
5. Choose the Settings tab.
6. Click the "Auto insert notification" option to enable.
7. Select OK until all Properties dialogs are closed, and restart Windows for the changes to take effect.

No sound is heard from speakers
Verify the following:

• Check the Microsoft Volume Control or the Audio Mixer Program mute options and volume sliders.
• Ensure the speakers are properly connected to the audio card’s output connector.
• Check the volume control and power connection of the speakers, if they are amplified. (Refer to the speakers documentation for detailed information).
• Ensure a hardware conflict does not exist between your audio card and another device in your system.
• PCI bus mastering devices may be interfering with the operation of the audio card. Temporarily remove non-essential PCI bus mastering devices. If the device is a display card, upgrade the display card drivers, or set the card to the default Windows VGA mode.

If you are experiencing no sound only during audio CD playback, see "No sound is heard from audio (music) CDs" above.

Static sounds are heard in wave files
Check to see if the static sounds are heard in all wave files. If the difficulty occurs only with certain games, refer to the software manufacturer’s documentation. To troubleshoot static sounds heard in all wave files:

• Try different resource settings for the audio card, or set the card to use low DMA.
• Move the audio card to another PCI slot. Feedback from the power supply or another device may be responsible.